Multiple message types and procedure for selection of a message type for a random access message in a two-step random access procedure

ABSTRACT

Various aspects of the present disclosure generally relate to wireless communication. In some aspects, a user equipment may determine a message type for a random access message associated with a two-step random access channel procedure. The message type may be either a first message type or a second message type that is different from the second message type. The message type may be determined based at least in part on whether a signal strength satisfies a signal strength threshold. The user equipment may transmit the random access message based at least in part on the determined message type. Numerous other aspects are provided.

CROSS-REFERENCE TO RELATED APPLICATION

This Patent Application claims priority to U.S. Provisional Patent Application No. 62/968,907, filed on Jan. 31, 2020, entitled “MULTIPLE MESSAGE TYPES AND PROCEDURE FOR SELECTION OF A MESSAGE TYPE FOR A RANDOM ACCESS MESSAGE IN A TWO-STEP RANDOM ACCESS PROCEDURE,” and assigned to the assignee hereof. The disclosure of the prior Application is considered part of and is incorporated by reference into this Patent Application.

FIELD OF THE DISCLOSURE

Aspects of the present disclosure generally relate to wireless communication and to techniques and apparatuses for multiple message types and a procedure for selection of a message type for a random access message in a two-step random access procedure.

BACKGROUND

Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasts. Typical wireless communication systems may employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, and/or the like). Examples of such multiple-access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency-division multiple access (FDMA) systems, orthogonal frequency-division multiple access (OFDMA) systems, single-carrier frequency-division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and Long Term Evolution (LTE). LTE/LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP).

A wireless communication network may include a number of base stations (BSs) that can support communication for a number of user equipment (UEs). A user equipment (UE) may communicate with a base station (BS) via the downlink and uplink. The downlink (or forward link) refers to the communication link from the BS to the UE, and the uplink (or reverse link) refers to the communication link from the UE to the BS. As will be described in more detail herein, a BS may be referred to as a Node B, a gNB, an access point (AP), a radio head, a transmit receive point (TRP), a New Radio (NR) BS, a 5G Node B, and/or the like.

The above multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different user equipment to communicate on a municipal, national, regional, and even global level. New Radio (NR), which may also be referred to as 5G, is a set of enhancements to the LTE mobile standard promulgated by the Third Generation Partnership Project (3GPP). NR is designed to better support mobile broadband Internet access by improving spectral efficiency, lowering costs, improving services, making use of new spectrum, and better integrating with other open standards using orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) (CP-OFDM) on the downlink (DL), using CP-OFDM and/or SC-FDM (e.g., also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink (UL), as well as supporting beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation. However, as the demand for mobile broadband access continues to increase, there exists a need for further improvements in LTE and NR technologies. Preferably, these improvements should be applicable to other multiple access technologies and the telecommunication standards that employ these technologies.

SUMMARY

In some aspects, a method of wireless communication, performed by a UE, may include determining a message type for a random access message associated with a two-step random access channel (RACH) procedure, wherein the message type is either a first message type or a second message type, the first message type being different from the second message type, and wherein the message type is determined based at least in part on whether a signal strength satisfies a signal strength threshold; and transmitting the random access message based at least in part on the determined message type.

In some aspects, a method of wireless communication, performed by a base station, may include receiving, from a UE, a random access message associated with a two-step RACH procedure; determining, based at least in part on the random access message, a message type of the random access message, wherein the message type is either a first message type or a second message type, the first message type being different from the second message type; and processing the random access message based at least in part on determining the message type of the random access message.

In some aspects, a UE for wireless communication may include a memory and one or more processors operatively coupled to the memory. The memory and the one or more processors may be configured to determine a message type for a random access message associated with a two-step RACH procedure, wherein the message type is either a first message type or a second message type, the first message type being different from the second message type, and wherein the message type is determined based at least in part on whether a signal strength satisfies a signal strength threshold; and transmit the random access message based at least in part on the determined message type.

In some aspects, a base station for wireless communication may include a memory and one or more processors operatively coupled to the memory. The memory and the one or more processors may be configured to receive, from a UE, a random access message associated with a two-step RACH procedure; determine, based at least in part on the random access message, a message type of the random access message, wherein the message type is either a first message type or a second message type, the first message type being different from the second message type; and process the random access message based at least in part on determining the message type of the random access message.

In some aspects, a non-transitory computer-readable medium may store one or more instructions for wireless communication. The one or more instructions, when executed by one or more processors of a UE, may cause the one or more processors to determine a message type for a random access message associated with a two-step RACH procedure, wherein the message type is either a first message type or a second message type, the first message type being different from the second message type, and wherein the message type is determined based at least in part on whether a signal strength satisfies a signal strength threshold; and transmit the random access message based at least in part on the determined message type.

In some aspects, a non-transitory computer-readable medium may store one or more instructions for wireless communication. The one or more instructions, when executed by one or more processors of a base station, may cause the one or more processors to receive, from a UE, a random access message associated with a two-step RACH procedure; determine, based at least in part on the random access message, a message type of the random access message, wherein the message type is either a first message type or a second message type, the first message type being different from the second message type; and process the random access message based at least in part on determining the message type of the random access message.

In some aspects, an apparatus for wireless communication may include means for determining a message type for a random access message associated with a two-step RACH procedure, wherein the message type is either a first message type or a second message type, the first message type being different from the second message type, and wherein the message type is determined based at least in part on whether a signal strength satisfies a signal strength threshold; and means for transmitting the random access message based at least in part on the determined message type.

In some aspects, an apparatus for wireless communication may include means for receiving, from a UE, a random access message associated with a two-step RACH procedure; means for determining, based at least in part on the random access message, a message type of the random access message, wherein the message type is either a first message type or a second message type, the first message type being different from the second message type; and means for processing the random access message based at least in part on determining the message type of the random access message.

Aspects generally include a method, apparatus, system, computer program product, non-transitory computer-readable medium, user equipment, base station, wireless communication device, and/or processing system as substantially described herein with reference to and as illustrated by the drawings and specification.

The foregoing has outlined rather broadly the features and technical advantages of examples according to the disclosure in order that the detailed description that follows may be better understood. Additional features and advantages will be described hereinafter. The conception and specific examples disclosed may be readily utilized as a basis for modifying or designing other structures for carrying out the same purposes of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. Characteristics of the concepts disclosed herein, both their organization and method of operation, together with associated advantages will be better understood from the following description when considered in connection with the accompanying figures. Each of the figures is provided for the purposes of illustration and description, and not as a definition of the limits of the claims.

BRIEF DESCRIPTION OF THE DRAWINGS

So that the above-recited features of the present disclosure can be understood in detail, a more particular description, briefly summarized above, may be had by reference to aspects, some of which are illustrated in the appended drawings. It is to be noted, however, that the appended drawings illustrate only certain typical aspects of this disclosure and are therefore not to be considered limiting of its scope, for the description may admit to other equally effective aspects. The same reference numbers in different drawings may identify the same or similar elements.

FIG. 1 is a block diagram conceptually illustrating an example of a wireless communication network, in accordance with various aspects of the present disclosure.

FIG. 2 is a block diagram conceptually illustrating an example of a base station in communication with a UE in a wireless communication network, in accordance with various aspects of the present disclosure.

FIG. 3 is a diagram illustrating an example of selection of a message type for a random access message in a two-step RACH procedure, in accordance with various aspects of the present disclosure.

FIG. 4 is a diagram illustrating an example process performed, for example, by a user equipment, in accordance with various aspects of the present disclosure.

FIG. 5 is a diagram illustrating an example process performed, for example, by a base station, in accordance with various aspects of the present disclosure.

FIG. 6 is a conceptual data flow diagram illustrating an example of a data flow between different components in an example apparatus.

FIG. 7 is a diagram illustrating an example of a hardware implementation for an apparatus employing a processing system.

FIG. 8 is a conceptual data flow diagram illustrating an example of a data flow between different components in an example apparatus.

FIG. 9 is a diagram illustrating an example of a hardware implementation for an apparatus employing a processing system.

DETAILED DESCRIPTION

Various aspects of the disclosure are described more fully hereinafter with reference to the accompanying drawings. This disclosure may, however, be embodied in many different forms and should not be construed as limited to any specific structure or function presented throughout this disclosure. Rather, these aspects are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art. Based on the teachings herein one skilled in the art should appreciate that the scope of the disclosure is intended to cover any aspect of the disclosure disclosed herein, whether implemented independently of or combined with any other aspect of the disclosure. For example, an apparatus may be implemented or a method may be practiced using any number of the aspects set forth herein. In addition, the scope of the disclosure is intended to cover such an apparatus or method which is practiced using other structure, functionality, or structure and functionality in addition to or other than the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of a claim.

Several aspects of telecommunication systems will now be presented with reference to various apparatuses and techniques. These apparatuses and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, and/or the like (collectively referred to as “elements”). These elements may be implemented using hardware, software, or combinations thereof. Whether such elements are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system.

It should be noted that while aspects may be described herein using terminology commonly associated with 3G and/or 4G wireless technologies, aspects of the present disclosure can be applied in other generation-based communication systems, such as 5G and later, including NR technologies.

FIG. 1 is a diagram illustrating a wireless network 100 in which aspects of the present disclosure may be practiced. The wireless network 100 may be an LTE network or some other wireless network, such as a 5G or NR network. The wireless network 100 may include a number of BSs 110 (shown as BS 110 a, BS 110 b, BS 110 c, and BS 110 d) and other network entities. ABS is an entity that communicates with user equipment (UEs) and may also be referred to as a base station, a NR BS, a Node B, a gNB, a 5G node B (NB), an access point, a transmit receive point (TRP), and/or the like. Each BS may provide communication coverage for a particular geographic area. In 3GPP, the term “cell” can refer to a coverage area of a BS and/or a BS subsystem serving this coverage area, depending on the context in which the term is used.

A BS may provide communication coverage for a macro cell, a pico cell, a femto cell, and/or another type of cell. A macro cell may cover a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs with service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs with service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UEs having association with the femto cell (e.g., UEs in a closed subscriber group (CSG)). ABS for a macro cell may be referred to as a macro BS. ABS for a pico cell may be referred to as a pico BS. A BS for a femto cell may be referred to as a femto BS or a home BS. In the example shown in FIG. 1, a BS 110 a may be a macro BS for a macro cell 102 a, a BS 110 b may be a pico BS for a pico cell 102 b, and a BS 110 c may be a femto BS for a femto cell 102 c. A BS may support one or multiple (e.g., three) cells. The terms “eNB”, “base station”, “NR BS”, “gNB”, “TRP”, “AP”, “node B”, “5G NB”, and “cell” may be used interchangeably herein.

In some aspects, a cell may not necessarily be stationary, and the geographic area of the cell may move according to the location of a mobile BS. In some aspects, the BSs may be interconnected to one another and/or to one or more other BSs or network nodes (not shown) in the wireless network 100 through various types of backhaul interfaces such as a direct physical connection, a virtual network, and/or the like using any suitable transport network.

Wireless network 100 may also include relay stations. A relay station is an entity that can receive a transmission of data from an upstream station (e.g., a BS or a UE) and send a transmission of the data to a downstream station (e.g., a UE or a BS). A relay station may also be a UE that can relay transmissions for other UEs. In the example shown in FIG. 1, a relay station 110 d may communicate with macro BS 110 a and a UE 120 d in order to facilitate communication between BS 110 a and UE 120 d. A relay station may also be referred to as a relay BS, a relay base station, a relay, and/or the like.

Wireless network 100 may be a heterogeneous network that includes BSs of different types, e.g., macro BSs, pico BSs, femto BSs, relay BSs, and/or the like. These different types of BSs may have different transmit power levels, different coverage areas, and different impacts on interference in wireless network 100. For example, macro BSs may have a high transmit power level (e.g., 5 to 40 Watts) whereas pico BSs, femto BSs, and relay BSs may have lower transmit power levels (e.g., 0.1 to 2 Watts).

A network controller 130 may couple to a set of BSs and may provide coordination and control for these BSs. Network controller 130 may communicate with the BSs via a backhaul. The BSs may also communicate with one another, e.g., directly or indirectly via a wireless or wireline backhaul.

UEs 120 (e.g., 120 a, 120 b, 120 c) may be dispersed throughout wireless network 100, and each UE may be stationary or mobile. A UE may also be referred to as an access terminal, a terminal, a mobile station, a subscriber unit, a station, and/or the like. A UE may be a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device or equipment, biometric sensors/devices, wearable devices (smart watches, smart clothing, smart glasses, smart wrist bands, smart jewelry (e.g., smart ring, smart bracelet)), an entertainment device (e.g., a music or video device, or a satellite radio), a vehicular component or sensor, smart meters/sensors, industrial manufacturing equipment, a global positioning system device, or any other suitable device that is configured to communicate via a wireless or wired medium.

Some UEs may be considered machine-type communication (MTC) or evolved or enhanced machine-type communication (eMTC) UEs. MTC and eMTC UEs include, for example, robots, drones, remote devices, sensors, meters, monitors, location tags, and/or the like, that may communicate with a base station, another device (e.g., remote device), or some other entity. A wireless node may provide, for example, connectivity for or to a network (e.g., a wide area network such as Internet or a cellular network) via a wired or wireless communication link. Some UEs may be considered Internet-of-Things (IoT) devices, and/or may be implemented as NB-IoT (narrowband internet of things) devices. Some UEs may be considered a Customer Premises Equipment (CPE). UE 120 may be included inside a housing that houses components of UE 120, such as processor components, memory components, and/or the like.

In general, any number of wireless networks may be deployed in a given geographic area. Each wireless network may support a particular radio access technology (RAT) and may operate on one or more frequencies. A RAT may also be referred to as a radio technology, an air interface, and/or the like. A frequency may also be referred to as a carrier, a frequency channel, and/or the like. Each frequency may support a single RAT in a given geographic area in order to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.

In some aspects, two or more UEs 120 (e.g., shown as UE 120 a and UE 120 e) may communicate directly using one or more sidelink channels (e.g., without using a base station 110 as an intermediary to communicate with one another). For example, the UEs 120 may communicate using peer-to-peer (P2P) communications, device-to-device (D2D) communications, a vehicle-to-everything (V2X) protocol (e.g., which may include a vehicle-to-vehicle (V2V) protocol, a vehicle-to-infrastructure (V2I) protocol, and/or the like), a mesh network, and/or the like. In this case, the UE 120 may perform scheduling operations, resource selection operations, and/or other operations described elsewhere herein as being performed by the base station 110.

In some aspects, a UE 120 and/or a base station 110 may perform one or more operations associated with selecting a message type, of multiple message types, for a random access message in a two-step random access procedure. For example, the UE 120 may determine a message type for a random access message associated with the two-step RACH procedure, as described herein. In some aspects, the message type may be either a first message type (e.g., msgA) or a second message type (e.g., a coverage enhanced msgA), and the UE 120 may determine the message type based at least in part on whether a signal strength satisfies a threshold. After determining the message type, the UE 120 may transmit the random access message accordingly. In some aspects, a base station 110 may receive the random access message associated with the two-step RACH procedure, determine the message type, and process the random access message accordingly, as described herein. In this way, benefits provided by the two-step RACH procedure (e.g., reduction in signaling overhead and/or latency, improvement in RACH capacity and/or power efficiency) can be realized, while coverage of the random access message may be increased.

As indicated above, FIG. 1 is provided as an example. Other examples may differ from what is described with regard to FIG. 1.

FIG. 2 shows a block diagram of a design 200 of base station 110 and UE 120, which may be one of the base stations and one of the UEs in FIG. 1. Base station 110 may be equipped with T antennas 234 a through 234 t, and UE 120 may be equipped with R antennas 252 a through 252 r, where in general T≥1 and R≥1.

At base station 110, a transmit processor 220 may receive data from a data source 212 for one or more UEs, select one or more modulation and coding schemes (MCS) for each UE based at least in part on channel quality indicators (CQIs) received from the UE, process (e.g., encode and modulate) the data for each UE based at least in part on the MCS(s) selected for the UE, and provide data symbols for all UEs. Transmit processor 220 may also process system information (e.g., for semi-static resource partitioning information (SRPI) and/or the like) and control information (e.g., CQI requests, grants, upper layer signaling, and/or the like) and provide overhead symbols and control symbols. Transmit processor 220 may also generate reference symbols for reference signals (e.g., the cell-specific reference signal (CRS)) and synchronization signals (e.g., the primary synchronization signal (PSS) and secondary synchronization signal (SSS)). A transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on the data symbols, the control symbols, the overhead symbols, and/or the reference symbols, if applicable, and may provide T output symbol streams to T modulators (MODs) 232 a through 232 t. Each modulator 232 may process a respective output symbol stream (e.g., for OFDM and/or the like) to obtain an output sample stream. Each modulator 232 may further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal. T downlink signals from modulators 232 a through 232 t may be transmitted via T antennas 234 a through 234 t, respectively. According to various aspects described in more detail below, the synchronization signals can be generated with location encoding to convey additional information.

At UE 120, antennas 252 a through 252 r may receive the downlink signals from base station 110 and/or other base stations and may provide received signals to demodulators (DEMODs) 254 a through 254 r, respectively. Each demodulator 254 may condition (e.g., filter, amplify, downconvert, and digitize) a received signal to obtain input samples. Each demodulator 254 may further process the input samples (e.g., for OFDM and/or the like) to obtain received symbols. A MIMO detector 256 may obtain received symbols from all R demodulators 254 a through 254 r, perform MIMO detection on the received symbols if applicable, and provide detected symbols. A receive processor 258 may process (e.g., demodulate and decode) the detected symbols, provide decoded data for UE 120 to a data sink 260, and provide decoded control information and system information to a controller/processor 280. A channel processor may determine reference signal received power (RSRP), received signal strength indicator (RSSI), reference signal received quality (RSRQ), channel quality indicator (CQI), and/or the like. In some aspects, one or more components of UE 120 may be included in a housing.

On the uplink, at UE 120, a transmit processor 264 may receive and process data from a data source 262 and control information (e.g., for reports comprising RSRP, RSSI, RSRQ, CQI, and/or the like) from controller/processor 280. Transmit processor 264 may also generate reference symbols for one or more reference signals. The symbols from transmit processor 264 may be precoded by a TX MIMO processor 266 if applicable, further processed by modulators 254 a through 254 r (e.g., for DFT-s-OFDM, CP-OFDM, and/or the like), and transmitted to base station 110. At base station 110, the uplink signals from UE 120 and other UEs may be received by antennas 234, processed by demodulators 232, detected by a MIMO detector 236 if applicable, and further processed by a receive processor 238 to obtain decoded data and control information sent by UE 120. Receive processor 238 may provide the decoded data to a data sink 239 and the decoded control information to controller/processor 240. Base station 110 may include communication unit 244 and communicate to network controller 130 via communication unit 244. Network controller 130 may include communication unit 294, controller/processor 290, and memory 292.

Controller/processor 240 of base station 110, controller/processor 280 of UE 120, and/or any other component(s) of FIG. 2 may perform one or more techniques associated with multiple message types and a procedure for selection of a message type for a random access message in a two-step random access procedure, as described in more detail elsewhere herein. For example, controller/processor 240 of base station 110, controller/processor 280 of UE 120, and/or any other component(s) of FIG. 2 may perform or direct operations of, for example, process 4 of FIG. 4 and/or other processes as described herein. Memories 242 and 282 may store data and program codes for base station 110 and UE 120, respectively. In some aspects, memory 242 and/or memory 282 may comprise a non-transitory computer-readable medium storing one or more instructions for wireless communication. For example, the one or more instructions, when executed by one or more processors of the base station 110 and/or the UE 120, may perform or direct operations of, for example, process 400 of FIG. 4 and/or other processes as described herein. A scheduler 246 may schedule UEs for data transmission on the downlink and/or uplink.

In some aspects, UE 120 may include means for determining a message type for a random access message associated with a two-step RACH procedure, wherein the message type is either a first message type or a second message type, the first message type being different from the second message type, and wherein the message type is determined based at least in part on whether a signal strength satisfies a signal strength threshold; means for transmitting the random access message based at least in part on the determined message type; and/or the like. In some aspects, such means may include one or more components of UE 120 described in connection with FIG. 2, such as controller/processor 280, transmit processor 264, TX MIMO processor 266, MOD 254, antenna 252, DEMOD 254, MIMO detector 256, receive processor 258, and/or the like.

In some aspects, base station 110 may include means for receiving, from a UE 120, a random access message associated with a two-step RACH procedure; means for determining, based at least in part on the random access message, a message type of the random access message, wherein the message type is either a first message type or a second message type, the first message type being different from the second message type; means for processing the random access message based at least in part on determining the message type of the random access message; and/or the like. In some aspects, such means may include one or more components of base station 110 described in connection with FIG. 2, such as antenna 234, DEMOD 232, MIMO detector 236, receive processor 238, controller/processor 240, transmit processor 220, TX MIMO processor 230, MOD 232, antenna 234, and/or the like.

As indicated above, FIG. 2 is provided as an example. Other examples may differ from what is described with regard to FIG. 2.

A two-step RACH procedure includes two steps (rather than four steps, as in a traditional four-step RACH procedure). The two-step RACH procedure can, in some cases, provide a reduction in signaling overhead and/or latency, and can provide improvement in RACH capacity and/or power efficiency. In the two-step RACH procedure, a UE transmits a random access message (referred to as msgA) that includes a preamble and a payload (e.g., a physical uplink shared channel (PUSCH) payload) of a configurable size (e.g., from a few bytes to a few hundred bytes). The preamble may assist with a timing offset estimation performed by a base station. In general, the UE transmits the preamble and then transmits the payload after a configurable amount of time (e.g., including a guard period and/or a transmission gap). Here, the configurable amount of time may serve to mitigate interference (e.g., inter-symbol interference (ISI), inter-carrier interference (ICI), and/or the like). The preamble and the payload can be transmitted in the same slot or in different slots.

Multiple UEs performing the two-step RACH procedure can share a same PUSCH occasion. That is, multiple UEs performing the two-step RACH procedure can share a same set of resources for transmitting random access message payloads. Such sharing may occur when, for example, the random access messages of the multiple UEs use similar modulation and coding schemes (MCSs), similar waveforms, or similar payload sizes. Resource allocation for a given PUSCH occasion can be specified relative to a RACH occasion (e.g., a set of resources for transmitting random access message preambles), for example, by semi-statically or dynamically configured offsets in time and/or frequency. Both separate and shared RACH occasions can be configured for two-step RACH. Further, when a RACH occasion is shared between a two-step RACH procedure and a four-step RACH procedure, a pool of preambles can be partitioned into mutually exclusive subsets, each of which is associated with a different type of RACH procedure.

A base station may receive the random access message associated with the two-step RACH procedure, and may detect the preamble and decode the payload. The base station may then transmit a random access response (referred to as msgB) to the UE. The random access response includes a physical downlink control channel (PDCCH) communication and a physical downlink shared channel (PDSCH) payload. Here, the PDCCH communication identifies a set of resources of the PDSCH payload that carries information for the UE. The PDSCH payload can include, for example, contention resolution information for the UE, a cell radio network temporary identifier (C-RNTI) for the UE, a timing advance (TA) command for the UE, and/or the like.

As described above, the aim of the two-step RACH procedure is to provide a reduction in signaling overhead and/or latency, and an improvement in RACH capacity and/or power efficiency (e.g., as compared to the four-step RACH procedure). It is therefore desirable to enable increased coverage of the random access message of the two-step RACH procedure (e.g., to allow the two-step RACH procedure to be used, while achieving acceptable coverage). In some cases, coverage enhancement for the random access message of the two-step RACH procedure can be provided by supporting used of different message types for the random access message.

Some techniques and apparatuses described herein provide techniques and apparatuses for selection of a message type for a random access message in a two-step RACH procedure. In some aspects, a UE may determine the message type for the random access message associated with the two-step RACH procedure, where the message type is either a first message type (e.g., msgA) or a second message type (e.g., a coverage enhanced msgA). In some aspects, the UE may determine the message type based at least in part on whether a signal strength satisfies a signal strength threshold. In this way, the above-described benefits of the two-step RACH procedure can be realized, while coverage of the random access message may be increased. Additional details are described below.

FIG. 3 is a diagram illustrating an example 300 of selection of a message type for a random access message in a two-step RACH procedure, in accordance with various aspects of the present disclosure.

As shown in FIG. 3 by reference 305, a base station (e.g., base station 110) may transmit a synchronization signal block (SSB) (e.g., using transmit processor 220, controller/processor 240, memory 242, transmission component 810, and/or the like). In some aspects, the SSB may include one or more synchronization signals and a physical broadcast channel (PBCH), as described below. In general, in association with transmitting a set of SSBs, the base station defines candidate positions for SSBs to be transmitted within a radio frame, and the quantity of candidate positions corresponds to a quantity of beams radiated in a given direction. Here, each SSB transmitted by the base station may be associated with a respective SSB index. As further indicated by reference 305, a UE (e.g., UE 120) may receive (e.g., using receive processor 258, controller/processor 280, memory 282, reception component 604, and/or the like) an SSB transmitted by the base station.

As shown by reference 310, the UE may determine (e.g., using receive processor 258, controller/processor 280, memory 282, determination component 606, and/or the like) a signal strength based at least in part on a reference signal received power (RSRP) associated with the SSB. In some aspects, the UE may measure a signal strength of a reference signal (e.g., a demodulation reference signal (DMRS)) of each SSB detected by the UE (e.g., within a particular period of time, such as a period of one SSB set) and, based on results of these measurements, may identify an SSB for which the reference signal has a suitable (e.g., strongest) signal strength. Here, the SSB with the suitable signal strength uses a suitable (e.g., best) beam for the UE.

In some aspects, after identifying the suitable beam, the UE may then decode the PBCH associated with the SSB. The PBCH may carry, for example, system information (e.g., a master information block (MIB), one or more system information blocks (SIBs), and/or the like), a configuration for remaining minimum system information (RMSI), and one or more other items of information. Here, decoding the PBCH enables the UE to receive a subsequent physical downlink control channel (PDCCH) and a physical downlink shared channel (PDSCH) that schedule and carry, respectively, RMSI and other system information (OSI). In some aspects, the configuration of the PDCCH for the RMSI may be determined from the PBCH, and a control resource set (CORESET) configuration for the RMSI may be determined based at least in part on an SSB index of the SSB.

In some aspects, the UE may determine, based at least in part on the signal strength, that the UE is to use a two-step RACH procedure in association with accessing the wireless communication system. In some aspects, the UE may determine that the UE is to use the two-step RACH procedure based at least in part on a signal strength threshold associated with identifying a RACH procedure (herein referred to as threshold Th2). For example, the UE may determine the signal strength based at least in part on the RSRP associated with the SSB, as described above. The UE may then compare the signal strength to the threshold Th2. Here, if the signal strength satisfies the threshold Th2 (e.g., when the signal strength is greater than or equal to the threshold Th2), then the UE may determine that the UE is to use the two-step RACH procedure. Conversely, if the signal strength does not satisfy the threshold Th2 (e.g., when the signal strength is less than the threshold Th2), then the UE may determine that the UE is to use a four-step RACH procedure. For the purposes of the example shown in FIG. 3, the UE has determined that the UE is to use the two-step RACH procedure (i.e., that the signal strength satisfies threshold Th2).

As indicated by reference 315, the UE may determine (e.g., using receive processor 258, transmit processor 264, controller/processor 280, memory 282, determination component 606, and/or the like) a message type for a random access message associated with the two-step RACH procedure. In some aspects, the message type may be either a first message type or a second message type. In some aspects, the first message type may be a message type of a first message in the two-step RACH procedure (e.g., msgA) and the second message type may be a coverage enhanced message type of the first message in the two-step RACH procedure (e.g., a coverage enhanced msgA).

In some aspects, the UE may determine the message type based at least in part on whether the signal strength satisfies a signal strength threshold associated with identifying a message type of a random access message for a two-step RACH procedure (herein referred to threshold Th1). In some aspects, the threshold TH1 may be greater than the threshold Th2 described above. As an example, the UE may determine the signal strength based at least in part on the RSRP associated with the SSB, as described above. The UE may then compare the signal strength to the threshold TH1. Here, if the signal strength satisfies the threshold Th1 (e.g., when the signal strength is greater than or equal to the threshold Th1), then the UE may determine that the UE is to use the first message type (e.g., msgA) for the random access message of the two-step RACH procedure. Conversely, if the signal strength does not satisfy the threshold Th1 (e.g., when the signal strength is less than the threshold Th1), then the UE may determine that the UE is to the second message type (e.g., coverage enhanced msgA) for the random access message of the two-step RACH procedure. In some aspects, the threshold TH1 may be identified in system information (e.g., RMSI) received by the UE from the base station in the manner described above. Thus, in some implementations, the threshold TH1 (and also the threshold Th2) may be configured on the UE by the base station.

In some aspects, one or more characteristics of the first message type may be different from one or more characteristics of the second message type. For example, a physical random access channel (PRACH) format associated with the first message type may be different from a PRACH format associated with the second message type. As another example, PUSCH repetition (i.e., repetition of the PUSCH payload within msgA) may not be applied for the first message type, and PUSCH repetition may be applied for the second message type. As another example, an MCS associated with the first message type may be different from an MCS associated with the second message type. As another example, a payload size associated with the first message type may be different from a payload size associated with the second message type. As another example, a PUSCH resource allocation associated with the first message type may be different from a PUSCH resource allocation size associated with the second message type. As another example, preamble repetition (i.e., repetition of the preamble of msgA) may not be applied for the first message type, and preamble repetition may be applied for the second message type. As another example, a length of a preamble for the first message type may be less than a length of a preamble for the second message type. In some aspects, the one or more characteristics of the second message type may be selected or designed so as to provide coverage enhancement as compared to the first message type. That is, the one or more characteristics of the second message type may enable a random access message of the second message type to be a coverage enhanced random access message for the two-step RACH procedure.

In some aspects, the UE may receive configuration information associated with the second message type. The configuration information may include information associated with one or more of the above-described characteristics. For example, the configuration information associated with the second message type may include information associated with a PRACH format for the second message type, application of PUSCH repetition for the second message type, an MCS for the second message type, a payload size for the second message type, a resource allocation of a PUSCH for the second message type, application of preamble repetition for the second message type, a length of a preamble for the second message type, and/or the like. In some aspects, the configuration information may be transmitted by the base station, and received by the UE, in the SSB, the system information, the PDCCH, the RMSI, and/or like.

As shown by reference 320, the UE may transmit (e.g., using transmit processor 264, controller/processor 280, memory 282, transmission component 608, and/or the like) the random access message, associated with the two-step RACH procedure, based at least in part on the determined message type. For example, the UE may transmit the random access message using the first message type when the UE determines that the first message type is to be used for the random access message of the two-step RACH procedure. Alternatively, the UE may transmit the random access message using the second message type (e.g., based at least in part on the configuration associated with the second message type) when the UE determines that the second message type is to be used for the random access message of the two-step RACH procedure.

In some aspects, a preamble sequence included in the random access message may indicate whether PUSCH repetition was applied when transmitting the random access message. In such a case, the preamble sequence may be one of a set of preamble sequences associated with indicating application of PUSCH repetition. Thus, in some aspects, the application of PUSCH repetition may be linked to a subset of preamble sequences.

In some aspects, a format of a preamble of the random access message may indicate whether PUSCH repetition was applied when transmitting the random access message. Thus, in some aspects, the application of PUSCH repetition may be linked to the format of the preamble.

In some aspects, a format of a preamble of the random access message indicates an MCS for the PUSCH included in the random access message. Thus, in some aspects, the application of different MCSs for PUSCH may be linked to the format of the preamble.

In some aspects, preamble repetition of the random access message may indicate whether PUSCH repetition was applied when transmitting the random access message. Thus, in some aspects, the application of PUSCH repetition may be linked to preamble repetition.

In some aspects, a length of a preamble of the random access message may indicate whether PUSCH repetition was applied when transmitting the random access message. Thus, in some aspects, the application of PUSCH repetition may be linked to the length of the preamble.

In some aspects, a resource allocation of a PUSCH occasion and a selection of a PUSCH resource unit, relative to a RACH occasion, may be based at least in part on whether the signal strength satisfies the threshold TH1. That is, in some aspects, a resource allocation of a PUSCH occasion and a selection of a PUSCH resource unit, relative to a RACH occasion, may differ depending on the message type. In some aspects, information associated with the resource allocation of the PUSCH occasion and the selection of the PUSCH resource unit, relative to the RACH occasion, may be identified in the system information received by the UE.

As shown by reference 325, the base station may receive (e.g., using receive processor 238, controller/processor 240, memory 242, reception component 804, and/or the like) the random access message associated with the two-step RACH procedure. The base station may then determine (e.g., using receive processor 238, controller/processor 240, memory 242, determination component 806, and/or the like) the message type of the random access message. For example, the base station may determine the message type based at least in part on the format of the preamble (e.g., when the format of the preamble is a format associated with a given message type). As another example, the base station may determine the message type based at least in part on a preamble sequence of the random access message (e.g., when the preamble sequence is one of a set of preamble sequences associated with a given message type). As another example, the base station may determine the message type based at least in part on a length of a preamble of the random access message (e.g., when the length of the preamble is associated with a given message type). As another example, the base station may determine the message type based at least in part on whether preamble repetition was applied for the random access message (e.g., when application of preamble repetition is indicative of a given message type). As another example, the base station may determine the message type based at least in part on a set of resources in which the random access message is received (e.g., when a set of resources in which random access messages are communicated is dependent on message type).

As shown by reference 330, the base station may process (e.g., using transmit processor 220, receive processor 238, controller/processor 240, memory 242, processing component 808, and/or the like) the random access message based at least in part on determining the message type of the random access message. For example, after determining the message type, the base station may determine a configuration of the random access message that identifies one or more characteristics of the message type (e.g., PRACH format, PUSCH repetition, MCS, payload size, PUSCH resource allocation), and may decode the random access message according to the configuration. After decoding the random access message, the base station may then proceed with the two-step RACH procedure (e.g., by preparing and transmitting msgB).

As indicated above, FIG. 3 is provided as an example. Other examples may differ from what is described with respect to FIG. 3.

FIG. 4 is a diagram illustrating an example process 400 performed, for example, by a UE, in accordance with various aspects of the present disclosure. Example process 400 is an example where the UE (e.g., UE 120 and/or the like) performs operations associated with selection of a message type for a random access message in a two-step RACH procedure.

As shown in FIG. 4, in some aspects, process 400 may include determining a message type for a random access message associated with a two-step RACH procedure (block 410). For example, the UE (e.g., using receive processor 258, transmit processor 264, controller/processor 280, memory 282, and/or the like) may determine a message type for a random access message associated with a two-step RACH procedure (e.g., as described above in association with reference 315 of FIG. 3). In some aspects, the message type is either a first message type or a second message type, the first message type being different from the second message type. In some aspects, the message type is determined based at least in part on whether a signal strength satisfies a signal strength threshold.

As further shown in FIG. 4, in some aspects, process 400 may include transmitting the random access message based at least in part on the determined message type (block 420). For example, the UE (e.g., using transmit processor 264, controller/processor 280, memory 282, and/or the like) may transmit the random access message based at least in part on the determined message type (e.g., as described above in association with reference 320 of FIG. 3).

Process 400 may include additional aspects, such as any single aspect or any combination of aspects described below and/or in connection with one or more other processes described elsewhere herein.

In a first aspect, the message type is determined to be the first message type when the signal strength satisfies the signal strength threshold, and is determined to be the second message type when the signal strength does not satisfy the signal strength threshold.

In a second aspect, alone or in combination with the first aspect, the first message type includes a message type of a first message in the two-step RACH procedure and the second message type includes a coverage enhanced message type of the first message in the two-step RACH procedure.

In a third aspect, alone or in combination with one or more of the first and second aspects, the signal strength threshold is identified in system information received by the UE from a base station.

In a fourth aspect, alone or in combination with one or more of the first through third aspects, the system information is carried by remaining minimum system information.

In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, a PRACH format associated with the first message type is different from a PRACH format associated with the second message type.

In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, PUSCH repetition is not to be applied for the first message type, and PUSCH repetition is to be applied for the second message type.

In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, an MCS associated with the first message type is different from an MCS associated with the second message type.

In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, a payload size associated with the first message type is different from a payload size associated with the second message type.

In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, a PUSCH resource allocation associated with the first message type is different from a PUSCH resource allocation size associated with the second message type.

In a tenth aspect, alone or in combination with one or more of the first through ninth aspects, a preamble sequence included in the random access message indicates whether PUSCH repetition was applied when transmitting the random access message, the preamble sequence being one of a set of preamble sequences associated with indicating application of PUSCH repetition.

In an eleventh aspect, alone or in combination with one or more of the first through tenth aspects, a format of a preamble of the random access message indicates whether physical uplink shared channel repetition was applied when transmitting the random access message.

In a twelfth aspect, alone or in combination with one or more of the first through eleventh aspects, a format of a preamble of the random access message indicates a modulation and coding scheme for a physical uplink shared channel included in the random access message.

In a thirteenth aspect, alone or in combination with one or more of the first through twelfth aspects, a resource allocation of a PUSCH occasion and a selection of a PUSCH resource unit, relative to a RACH occasion, is based at least in part on whether the signal strength satisfies the signal strength threshold.

In a fourteenth aspect, alone or in combination with one or more of the first through thirteenth aspects, information associated with the resource allocation of the PUSCH occasion and the selection of the PUSCH resource unit, relative to the RACH occasion, is identified in system information received by the UE.

In a fifteenth aspect, alone or in combination with one or more of the first through fourteenth aspects, process 400 includes receiving an SSB, and determining the signal strength based at least in part on a reference signal received power associated with the SSB.

In a sixteenth aspect, alone or in combination with one or more of the first through fifteenth aspects, process 400 includes receiving configuration information associated with the second message type, the configuration information including information associated with at least one of: a PRACH format; application of PUSCH repetition; an MCS; a payload size; a resource allocation for PUSCH, application of preamble repetition; or a preamble length.

In a seventeenth aspect, alone or in combination with one or more of the first through sixteenth aspects, the configuration information is received in at least one of: an SSB; system information; a PDCCH; or RMSI.

In an eighteenth aspect, alone or in combination with one or more of the first through seventeenth aspects, process 400 includes determining, based at least in part on another signal strength threshold, that the two-step RACH procedure is to be used in association with accessing a wireless communication system.

In a nineteenth aspect, alone or in combination with one or more of the first through eighteenth aspects, the random access message is msgA.

In a twentieth aspect, alone or in combination with one or more of the first through nineteenth aspects, preamble repetition is not to be applied for the first message type, and preamble repetition is to be applied for the second message type.

In a twenty-first aspect, alone or in combination with one or more of the first through twentieth aspects, a preamble length associated with the first message type is different from a preamble length associated with the second message type

Although FIG. 4 shows example blocks of process 400, in some aspects, process 400 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in FIG. 4. Additionally, or alternatively, two or more of the blocks of process 400 may be performed in parallel.

FIG. 5 is a diagram illustrating an example process 500 performed, for example, by a base station, in accordance with various aspects of the present disclosure. Example process 500 is an example where the base station (e.g., base station 110 and/or the like) performs operations associated with selection of a message type for a random access message in a two-step RACH procedure.

As shown in FIG. 5, in some aspects, process 500 may include receiving, from a UE, a random access message associated with a two-step RACH procedure (block 510). For example, the base station (e.g., using transmit processor 220, controller/processor 240, memory 242, and/or the like) may receive, from a UE (e.g., UE 120), a random access message associated with a two-step RACH procedure (e.g., as described above in association with reference 325 of FIG. 3).

As further shown in FIG. 5, in some aspects, process 500 may include determining, based at least in part on the random access message, a message type of the random access message (block 520). For example, the base station (e.g., using transmit processor 220, receive processor 238, controller/processor 240, memory 242, and/or the like) may determine, based at least in part on the random access message, a message type of the random access message (e.g., as described above in association with reference 325 of FIG. 3). In some aspects, the message type is either a first message type or a second message type, the first message type being different from the second message type.

As further shown in FIG. 5, in some aspects, process 500 may include processing the random access message based at least in part on determining the message type of the random access message (block 530). For example, the base station (e.g., using transmit processor 220, receive processor 238, controller/processor 240, memory 242, and/or the like) may process the random access message based at least in part on determining the message type of the random access message (e.g., as described above in association with reference 330 of FIG. 3).

Process 500 may include additional aspects, such as any single aspect or any combination of aspects described below and/or in connection with one or more other processes described elsewhere herein.

In a first aspect, the first message type includes a message type of a first message in the two-step RACH procedure and the second message type includes a coverage enhanced message type of the first message in the two-step RACH procedure.

In a second aspect, alone or in combination with the first aspect, a signal strength threshold, associated with determining to use the second message type, is identified in system information transmitted by the base station.

In a third aspect, alone or in combination with one or more of the first and second aspects, the system information is carried by remaining minimum system information.

In a fourth aspect, alone or in combination with one or more of the first through third aspects, a PRACH format associated with the first message type is different from a PRACH format associated with the second message type.

In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, PUSCH repetition is not to be applied for the first message type and PUSCH repetition is to be applied for the second message type.

In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, an MCS associated with the first message type is different from an MCS associated with the second message type.

In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, a payload size associated with the first message type is different from a payload size associated with the second message type.

In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, a PUSCH resource allocation associated with the first message type is different from a PUSCH resource allocation size associated with the second message type.

In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, a preamble sequence included in the random access message indicates whether PUSCH repetition was applied when transmitting the random access message, the preamble sequence being one of a set of preamble sequences associated with indicating application of PUSCH repetition.

In a tenth aspect, alone or in combination with one or more of the first through ninth aspects, a format of a preamble of the random access message indicates whether physical uplink shared channel repetition was applied when transmitting the random access message.

In an eleventh aspect, alone or in combination with one or more of the first through tenth aspects, a format of a preamble of the random access message indicates a modulation and coding scheme for a physical uplink shared channel included in the random access message.

In a twelfth aspect, alone or in combination with one or more of the first through eleventh aspects, a resource allocation of a PUSCH occasion and a selection of a PUSCH resource unit, relative to a RACH occasion, is based at least in part on whether a signal strength satisfies a signal strength threshold.

In a thirteenth aspect, alone or in combination with one or more of the first through twelfth aspects, information associated with the resource allocation of the PUSCH occasion and the selection of the PUSCH resource unit, relative to the RACH occasion, is identified in system information transmitted by the base station.

In a fourteenth aspect, alone or in combination with one or more of the first through thirteenth aspects, process 500 includes transmitting an SSB to enable a determination of a signal strength based at least in part on a reference signal received power associated with the SSB.

In a fifteenth aspect, alone or in combination with one or more of the first through fourteenth aspects, process 500 includes transmitting configuration information associated with the second message type, the configuration information including information associated with at least one of: a PRACH format; application of PUSCH repetition; an MCS; a payload size; a resource allocation for PUSCH, application of preamble repetition; or a preamble length.

In a sixteenth aspect, alone or in combination with one or more of the first through fifteenth aspects, the configuration information is transmitted in at least one of: an SS; system information; a PDCCH; or RMSI.

In a seventeenth aspect, alone or in combination with one or more of the first through sixteenth aspects, the random access message is msgA.

In an eighteenth aspect, alone or in combination with one or more of the first through seventeenth aspects, preamble repetition is not to be applied for the first message type, and preamble repetition is to be applied for the second message type.

In a nineteenth aspect, alone or in combination with one or more of the first through eighteenth aspects, a preamble length associated with the first message type is different from a preamble length associated with the second message type

Although FIG. 5 shows example blocks of process 500, in some aspects, process 500 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in FIG. 5. Additionally, or alternatively, two or more of the blocks of process 500 may be performed in parallel.

FIG. 6 is a conceptual data flow diagram 600 illustrating a data flow between different components in an example apparatus 602. The apparatus 602 may be a UE (e.g., UE 120). In some aspects, the apparatus 602 includes a reception component 604, a determination component 606, and/or a transmission component 608.

In some aspects, one or more components of apparatus 602 may operate to perform one or more operations described herein. For example, reception component 604 may operate to receive an SSB transmitted by a base station (e.g., base station 110). Determination component 606 may operate to determine a signal strength based at least in part on an RSRP associated with the SSB, and determine a message type for a random access message associated with a two-step RACH procedure based at least in part on whether a signal strength satisfies a signal strength threshold. Transmission component 608 may operate to transmit (e.g., to base station 650) the random access message based at least in part on the determined message type.

The apparatus may include additional components that perform each of the blocks of the algorithm in the aforementioned process 400 of FIG. 4 and/or the like. Each block in the aforementioned process 400 of FIG. 4 and/or the like may be performed by a component and the apparatus may include one or more of those components. The components may be one or more hardware components specifically configured to carry out the stated processes/algorithm, implemented by a processor configured to perform the stated processes/algorithm, stored within a computer-readable medium for implementation by a processor, or some combination thereof.

The number and arrangement of components shown in FIG. 6 are provided as an example. In practice, there may be additional components, fewer components, different components, or differently arranged components than those shown in FIG. 6. Furthermore, two or more components shown in FIG. 6 may be implemented within a single component, or a single component shown in FIG. 6 may be implemented as multiple, distributed components. Additionally, or alternatively, a set of components (e.g., one or more components) shown in FIG. 6 may perform one or more functions described as being performed by another set of components shown in FIG. 6.

FIG. 7 is a diagram 700 illustrating an example of a hardware implementation for an apparatus 602′ employing a processing system 702. The apparatus 602′ may be a UE (e.g., a UE 120).

The processing system 702 may be implemented with a bus architecture, represented generally by the bus 704. The bus 704 may include any number of interconnecting buses and bridges depending on the specific application of the processing system 702 and the overall design constraints. The bus 704 links together various circuits including one or more processors and/or hardware components, represented by the processor 706, the components 604, 606, 608, and the computer-readable medium/memory 708. The bus 704 may also link various other circuits such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art, and therefore will not be described any further.

The processing system 702 may be coupled to a transceiver 710. The transceiver 710 is coupled to one or more antennas 712. The transceiver 710 provides a means for communicating with various other apparatuses over a transmission medium. The transceiver 710 receives a signal from the one or more antennas 712, extracts information from the received signal, and provides the extracted information to the processing system 702, specifically the reception component 604. In addition, the transceiver 710 receives information from the processing system 702, specifically the transmission component 608, and based at least in part on the received information, generates a signal to be applied to the one or more antennas 712. The processing system 702 includes a processor 706 coupled to a computer-readable medium/memory 708. The processor 706 is responsible for general processing, including the execution of software stored on the computer-readable medium/memory 708. The software, when executed by the processor 706, causes the processing system 702 to perform the various functions described herein for any particular apparatus. The computer-readable medium/memory 708 may also be used for storing data that is manipulated by the processor 706 when executing software. The processing system further includes at least one of the components 604, 606, and 608. The components may be software modules running in the processor 706, resident/stored in the computer readable medium/memory 708, one or more hardware modules coupled to the processor 706, or some combination thereof. The processing system 702 may be a component of the UE 120 and may include the memory 282 and/or at least one of the TX MIMO processor 266, the RX processor 258, and/or the controller/processor 280.

In some aspects, the apparatus 602/602′ for wireless communication includes means for determining a message type for a random access message associated with a two-step RACH procedure, wherein the message type is either a first message type or a second message type, the first message type being different from the second message type, and wherein the message type is determined based at least in part on whether a signal strength satisfies a signal strength threshold; means for transmitting the random access message based at least in part on the determined message type; and/or the like. The aforementioned means may be one or more of the aforementioned components of the apparatus 602 and/or the processing system 702 of the apparatus 602′ configured to perform the functions recited by the aforementioned means. As described elsewhere herein, the processing system 702 may include the TX MIMO processor 266, the RX processor 258, and/or the controller/processor 280. In one configuration, the aforementioned means may be the TX MIMO processor 266, the RX processor 258, and/or the controller/processor 280 configured to perform the functions and/or operations recited herein.

FIG. 7 is provided as an example. Other examples may differ from what is described in connection with FIG. 7.

FIG. 8 is a conceptual data flow diagram 800 illustrating a data flow between different components in an example apparatus 802. The apparatus 802 may be a base station (e.g., base station 110). In some aspects, the apparatus 802 includes a reception component 804, a determination component 806, a processing component 808, and/or a transmission component 810.

In some aspects, one or more components of apparatus 802 may operate to perform one or more operations described herein. For example, reception component 804 may operate to receive (e.g., from a UE 850) a random access message, associated with a two-step RACH procedure. Determination component 806 may determine, based at least in part on the random access message, a message type of the random access message. Processing component 808 may process the random access message based at least in part on determining the message type of the random access message. Transmission component 810 may transmit (e.g., to the UE 850) a random access response (e.g., msgB) associated with the random access message.

The apparatus may include additional components that perform each of the blocks of the algorithm in the aforementioned process 500 of FIG. 5 and/or the like. Each block in the aforementioned process 500 of FIG. 5 and/or the like may be performed by a component and the apparatus may include one or more of those components. The components may be one or more hardware components specifically configured to carry out the stated processes/algorithm, implemented by a processor configured to perform the stated processes/algorithm, stored within a computer-readable medium for implementation by a processor, or some combination thereof.

The number and arrangement of components shown in FIG. 8 are provided as an example. In practice, there may be additional components, fewer components, different components, or differently arranged components than those shown in FIG. 8. Furthermore, two or more components shown in FIG. 8 may be implemented within a single component, or a single component shown in FIG. 8 may be implemented as multiple, distributed components. Additionally, or alternatively, a set of components (e.g., one or more components) shown in FIG. 8 may perform one or more functions described as being performed by another set of components shown in FIG. 8.

FIG. 9 is a diagram 900 illustrating an example of a hardware implementation for an apparatus 802′ employing a processing system 902. The apparatus 802′ may be a base station (e.g., base station 110).

The processing system 902 may be implemented with a bus architecture, represented generally by the bus 904. The bus 904 may include any number of interconnecting buses and bridges depending on the specific application of the processing system 902 and the overall design constraints. The bus 904 links together various circuits including one or more processors and/or hardware components, represented by the processor 906, the components 804, 806, 808, 810 and the computer-readable medium/memory 908. The bus 904 may also link various other circuits such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art, and therefore will not be described any further.

The processing system 902 may be coupled to a transceiver 910. The transceiver 910 is coupled to one or more antennas 912. The transceiver 910 provides a means for communicating with various other apparatuses over a transmission medium. The transceiver 910 receives a signal from the one or more antennas 912, extracts information from the received signal, and provides the extracted information to the processing system 902, specifically the reception component 804. In addition, the transceiver 910 receives information from the processing system 902, specifically the transmission component 810, and based at least in part on the received information, generates a signal to be applied to the one or more antennas 912. The processing system 902 includes a processor 906 coupled to a computer-readable medium/memory 908. The processor 906 is responsible for general processing, including the execution of software stored on the computer-readable medium/memory 908. The software, when executed by the processor 906, causes the processing system 902 to perform the various functions described herein for any particular apparatus. The computer-readable medium/memory 908 may also be used for storing data that is manipulated by the processor 906 when executing software. The processing system further includes at least one of the components 804, 806, 808, and 810. The components may be software modules running in the processor 906, resident/stored in the computer readable medium/memory 908, one or more hardware modules coupled to the processor 906, or some combination thereof. The processing system 902 may be a component of the base station 110 and may include the memory 242 and/or at least one of the TX MIMO processor 230, the RX processor 238, and/or the controller/processor 240.

In some aspects, the apparatus 802/802′ for wireless communication includes means for receiving, from a UE 120, a random access message associated with a two-step RACH procedure; means for determining, based at least in part on the random access message, a message type of the random access message, wherein the message type is either a first message type or a second message type, the first message type being different from the second message type; means for processing the random access message based at least in part on determining the message type of the random access message; and/or the like. The aforementioned means may be one or more of the aforementioned components of the apparatus 802 and/or the processing system 902 of the apparatus 802′ configured to perform the functions recited by the aforementioned means. As described elsewhere herein, the processing system 902 may include the TX MIMO processor 230, the receive processor 238, and/or the controller/processor 240. In one configuration, the aforementioned means may be the TX MIMO processor 230, the receive processor 238, and/or the controller/processor 240 configured to perform the functions and/or operations recited herein.

FIG. 9 is provided as an example. Other examples may differ from what is described in connection with FIG. 9.

The following provides an overview of aspects of the present disclosure:

Aspect 1: A method of wireless communication performed by a user equipment (UE), comprising: determining a message type for a random access message associated with a two-step random access channel (RACH) procedure, wherein the message type is either a first message type or a second message type, the first message type being different from the second message type, and wherein the message type is determined based at least in part on whether a signal strength satisfies a signal strength threshold; and transmitting the random access message based at least in part on the determined message type.

Aspect 2: The method of aspect 1, wherein the message type is determined to be the first message type when the signal strength satisfies the signal strength threshold, and is determined to be the second message type when the signal strength does not satisfy the signal strength threshold.

Aspect 3: The method of any of aspects 1-2, wherein the first message type includes a message type of a first message in the two-step RACH procedure and the second message type includes a coverage enhanced message type of the first message in the two-step RACH procedure.

Aspect 4: The method of any of aspects 1-3, wherein the random access message is msgA.

Aspect 5: The method of any of aspects 1-4, further comprising receiving system information from the base station, wherein the signal strength threshold is identified in the system information received by the UE.

Aspect 6: The method of any of aspects 1-5, further comprising receiving the signal strength threshold in system information comprising remaining minimum system information.

Aspect 7: The method of any of aspects 1-6, wherein transmitting the random access message comprises transmitting with a physical random access channel (PRACH) format, wherein the PRACH format when the first message type is determined is different from the PRACH format when the second message type is determined.

Aspect 8: The method of any of aspects 1-7, wherein transmitting the random access message comprises applying physical uplink shared channel (PUSCH) repetition if the first message type is determined and not applying PUSCH repetition if the second message type is determined.

Aspect 9: The method of any of aspects 1-8, wherein transmitting the random access message comprises transmitting with a modulation and coding scheme (MCS), wherein the MCS when the first message type is determined is different from the MCS when the second message type is determined.

Aspect 10: The method of any of aspects 1-9, wherein transmitting the random access message comprises transmitting with a payload size, wherein the payload size when the first message type is determined is different from the payload size when the second message type is determined.

Aspect 11: The method of any of aspects 1-10, wherein transmitting the random access message comprises transmitting with a physical uplink shared channel (PUSCH) resource allocation, wherein the PUSCH resource allocation when the first message type is determined is different from the PUSCH resource allocation when the second message type is determined.

Aspect 12: The method of any of aspects 1-11, wherein transmitting the random access message comprises applying preamble repetition if the first message type is determined and not applying preamble repetition if the second message type is determined.

Aspect 13: The method of any of aspects 1-12, wherein transmitting the random access message comprises transmitting with a preamble length, wherein the preamble length when the first message type is determined is different from the preamble length when the second message type is determined.

Aspect 14: The method of any of aspects 1-13, wherein transmitting the random access message comprises transmitting using a preamble sequence, wherein the preamble sequence indicates whether physical uplink shared channel (PUSCH) repetition was applied when transmitting the random access message, the preamble sequence being one of a set of preamble sequences associated with indicating application of PUSCH repetition.

Aspect 15: The method of any of aspects 1-14 wherein transmitting the random access message comprises transmitting with a format of a preamble that indicates whether physical uplink shared channel repetition was applied when transmitting the random access message.

Aspect 16: The method of any of aspects 1-15, wherein transmitting the random access message comprises transmitting with a format of a preamble that indicates a modulation and coding scheme for a physical uplink shared channel included in the random access message.

Aspect 17: The method of any of aspects 1-16, further comprising determining whether the signal strength satisfies the signal strength threshold, wherein a resource allocation of a physical uplink shared channel (PUSCH) occasion and a selection of a PUSCH resource unit, relative to a RACH occasion, is based at least in part on the determination of whether the signal strength satisfies the signal strength threshold.

Aspect 18: The method of aspect 17, further comprising receiving system information that identifies information associated with the resource allocation of the PUSCH occasion and the selection of the PUSCH resource unit relative to the RACH occasion.

Aspect 19: The method of any of aspects 1-18, further comprising: receiving a synchronization signal block (SSB); and determining the signal strength based at least in part on a reference signal received power associated with the SSB.

Aspect 20: The method of any of aspects 1-19, further comprising: receiving configuration information associated with the second message type, the configuration information including information associated with at least one of: a physical random access channel (PRACH) format; application of physical uplink shared channel (PUSCH) repetition; a modulation and coding scheme; a payload size; a resource allocation for PUSCH; application of preamble repetition; or a preamble length.

Aspect 21: The method of aspect 20, further comprising receiving the configuration information in at least one of: a synchronization signal block; system information; a physical downlink control channel; or remaining minimum system information.

Aspect 22: The method of any of aspects 1-21, further comprising: determining, based at least in part on another signal strength threshold, that the two-step RACH procedure is to be used in association with accessing a wireless communication system.

Aspect 23: A method of wireless communication performed by a base station, comprising: receiving, from a user equipment (UE), a random access message associated with a two-step random access channel (RACH) procedure; determining, based at least in part on the random access message, a message type of the random access message, wherein the message type is either a first message type or a second message type, the first message type being different from the second message type; and processing the random access message based at least in part on determining the message type of the random access message.

Aspect 24: The method of aspect 23, wherein the first message type includes a message type of a first message in the two-step RACH procedure and the second message type includes a coverage enhanced message type of the first message in the two-step RACH procedure.

Aspect 25: The method of any of aspects 23-24, further comprising transmitting system information that identifies a signal strength threshold associated with determining to use the second message type.

Aspect 26: The method of any of aspects 23-25, further comprising transmitting the signal strength threshold in system information comprising remaining minimum system information.

Aspect 27: The method of any of aspects 23-26, wherein processing the random access message comprises processing based on a physical random access channel (PRACH) format, wherein the PRACH format when the first message type is determined is different from the PRACH format when the second message type is determined.

Aspect 28: The method of any of aspects 23-27, wherein processing the random access message comprises processing based on a determination of whether physical uplink shared channel (PUSCH) repetition is applied, wherein PUSCH repetition is determined not to be applied if the first message type is determined and PUSCH repetition is determined to be applied if the second message type is determined.

Aspect 29: The method of any of aspects 23-28, wherein processing the random access message comprises processing based on a modulation and coding scheme (MCS), wherein the MCS when the first message type is determined is different from the MCS when the second message type is determined.

Aspect 30: The method of any of aspects 23-29, wherein processing the random access message comprises processing based on a payload size, wherein the payload size when the first message type is determined is different from the payload size when the second message type is determined.

Aspect 31: The method of any of aspects 23-30, wherein processing the random access message comprises processing based on a PUSCH resource allocation, wherein the PUSCH resource allocation when the first message type is determined is different from the PUSCH resource allocation when the second message type is determined.

Aspect 32: The method of any of aspects 23-31, wherein processing the random access message comprises processing based on a determination of whether preamble repetition is applied, wherein preamble repetition is determined not to be applied if the first message type is determined and preamble repetition is determined to be applied if the second message type is determined.

Aspect 33: The method of any of aspects 23-32, wherein processing the random access message comprises processing based on a preamble length, wherein the preamble length when the first message type is determined is different from the preamble length when the second message type is determined.

Aspect 34: The method of any of aspects 23-33, wherein receiving the random access message comprises receiving an indication of whether physical uplink shared channel (PUSCH) repetition was applied when transmitting the random access message, wherein the indication is a preamble sequence included in the random access message, the preamble sequence being one of a set of preamble sequences associated with indicating application of PUSCH repetition.

Aspect 35: The method of any of aspects 23-34, wherein receiving the random access message comprises receiving an indication of whether physical uplink shared channel (PUSCH) repetition was applied when transmitting the random access message, wherein the indication is a format of a preamble of the random access message.

Aspect 36: The method of any of aspects 23-35, wherein receiving the random access message comprises receiving an indication of a modulation and coding scheme (MCS) for a physical uplink shard channel included in the random access message, wherein the indication is a format of a preamble of the random access message.

Aspect 37: The method of any of aspects 23-36, wherein a resource allocation of a physical uplink shared channel (PUSCH) occasion and a selection of a PUSCH resource unit, relative to a RACH occasion, is based at least in part on whether a signal strength satisfies a signal strength threshold.

Aspect 38: The method of aspect 37, further comprising transmitting system information that identifies information associated with the resource allocation of the PUSCH occasion and the selection of the PUSCH resource unit relative to the RACH occasion.

Aspect 39: The method of any of aspects 23-38, further comprising: transmitting a synchronization signal block (SSB) to enable a determination of a signal strength based at least in part on of a reference signal received power associated with the SSB.

Aspect 40: The method of any of aspects 23-39, further comprising: transmitting configuration information associated with the second message type, the configuration information including information associated with at least one of: a physical random access channel (PRACH) format; application of physical uplink shared channel (PUSCH) repetition; a modulation and coding scheme; a payload size; a resource allocation for PUSCH; application of preamble repetition; or a preamble length.

Aspect 41: The method of any of aspects 23-40, further comprising transmitting the configuration information in at least one of: a synchronization signal block; system information; a physical downlink control channel; or remaining minimum system information.

Aspect 42: An apparatus for wireless communication at a device, comprising a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method of one or more aspects of aspects 1-22.

Aspect 43: A device for wireless communication, comprising a memory and one or more processors coupled to the memory, the memory and the one or more processors configured to perform the method of one or more aspects of aspects 1-22.

Aspect 44: An apparatus for wireless communication, comprising at least one means for performing the method of one or more aspects of aspects 1-22.

Aspect 45: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method of one or more aspects of aspects 1-22.

Aspect 46: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method of one or more aspects of aspects 1-22.

Aspect 47: An apparatus for wireless communication at a device, comprising a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method of one or more aspects of aspects 23-41.

Aspect 48: A device for wireless communication, comprising a memory and one or more processors coupled to the memory, the memory and the one or more processors configured to perform the method of one or more aspects of aspects 23-41.

Aspect 49: An apparatus for wireless communication, comprising at least one means for performing the method of one or more aspects of aspects 23-41.

Aspect 50: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method of one or more aspects of aspects 23-41.

Aspect 51: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method of one or more aspects of aspects 23-41.

The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the aspects to the precise form disclosed. Modifications and variations may be made in light of the above disclosure or may be acquired from practice of the aspects.

As used herein, the term “component” is intended to be broadly construed as hardware, firmware, and/or a combination of hardware and software. As used herein, a processor is implemented in hardware, firmware, and/or a combination of hardware and software.

As used herein, satisfying a threshold may, depending on the context, refer to a value being greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, and/or the like.

It will be apparent that systems and/or methods described herein may be implemented in different forms of hardware, firmware, and/or a combination of hardware and software. The actual specialized control hardware or software code used to implement these systems and/or methods is not limiting of the aspects. Thus, the operation and behavior of the systems and/or methods were described herein without reference to specific software code—it being understood that software and hardware can be designed to implement the systems and/or methods based, at least in part, on the description herein.

Even though particular combinations of features are recited in the claims and/or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. In fact, many of these features may be combined in ways not specifically recited in the claims and/or disclosed in the specification. Although each dependent claim listed below may directly depend on only one claim, the disclosure of various aspects includes each dependent claim in combination with every other claim in the claim set. A phrase referring to “at least one of” a list of items refers to any combination of those items, including single members. As an example, “at least one of: a, b, or c” is intended to cover a, b, c, a-b, a-c, b-c, and a-b-c, as well as any combination with multiples of the same element (e.g., a-a, a-a-a, a-a-b, a-a-c, a-b-b, a-c-c, b-b, b-b-b, b-b-c, c-c, and c-c-c or any other ordering of a, b, and c).

No element, act, or instruction used herein should be construed as critical or essential unless explicitly described as such. Also, as used herein, the articles “a” and “an” are intended to include one or more items, and may be used interchangeably with “one or more.” Furthermore, as used herein, the terms “set” and “group” are intended to include one or more items (e.g., related items, unrelated items, a combination of related and unrelated items, and/or the like), and may be used interchangeably with “one or more.” Where only one item is intended, the phrase “only one” or similar language is used. Also, as used herein, the terms “has,” “have,” “having,” and/or the like are intended to be open-ended terms. Further, the phrase “based on” is intended to mean “based, at least in part, on” unless explicitly stated otherwise. 

What is claimed is:
 1. A method of wireless communication performed by a user equipment (UE), comprising: determining that the UE is to use a two-step random access channel (RACH) procedure based at least in part on a first signal strength threshold; determining a message type for a random access message associated with the two-step RACH procedure, wherein the message type is either a first message type or a second message type, the first message type being different from the second message type, wherein the message type is determined based at least in part on whether a signal strength satisfies a second signal strength threshold, and wherein the second signal threshold is greater than the first signal strength threshold; and transmitting the random access message based at least in part on the determined message type.
 2. The method of claim 1, wherein the message type is determined to be the first message type when the signal strength satisfies the second signal strength threshold, and is determined to be the second message type when the signal strength does not satisfy the second signal strength threshold.
 3. The method of claim 1, wherein the first message type includes a message type of a first message in the two-step RACH procedure and the second message type includes a coverage enhanced message type of the first message in the two-step RACH procedure.
 4. The method of claim 1, wherein the random access message is msgA.
 5. The method of claim 1, further comprising receiving system information from a base station, wherein the second signal strength threshold is identified in the system information received by the UE.
 6. The method of claim 1, further comprising receiving information identifying the second signal strength threshold in system information comprising remaining minimum system information.
 7. The method of claim 1, wherein transmitting the random access message comprises transmitting with a physical random access channel (PRACH) format, and wherein the PRACH format when the first message type is determined is different from the PRACH format when the second message type is determined.
 8. The method of claim 1, wherein transmitting the random access message comprises applying physical uplink shared channel (PUSCH) repetition if the first message type is determined and not applying PUSCH repetition if the second message type is determined.
 9. The method of claim 1, wherein transmitting the random access message comprises transmitting with a modulation and coding scheme (MCS), and wherein the MCS when the first message type is determined is different from the MCS when the second message type is determined.
 10. The method of claim 1, wherein transmitting the random access message comprises transmitting with a payload size, and wherein the payload size when the first message type is determined is different from the payload size when the second message type is determined.
 11. The method of claim 1, wherein transmitting the random access message comprises transmitting with a physical uplink shared channel (PUSCH) resource allocation, and wherein the PUSCH resource allocation when the first message type is determined is different from the PUSCH resource allocation when the second message type is determined.
 12. The method of claim 1, wherein transmitting the random access message comprises applying preamble repetition if the first message type is determined and not applying preamble repetition if the second message type is determined.
 13. The method of claim 1, wherein transmitting the random access message comprises transmitting with a preamble length, and wherein the preamble length when the first message type is determined is different from the preamble length when the second message type is determined.
 14. The method of claim 1, wherein transmitting the random access message comprises transmitting using a preamble sequence, and wherein the preamble sequence indicates whether physical uplink shared channel (PUSCH) repetition was applied when transmitting the random access message, the preamble sequence being one of a set of preamble sequences associated with indicating application of PUSCH repetition.
 15. The method of claim 1, wherein transmitting the random access message comprises transmitting with a format of a preamble that indicates whether physical uplink shared channel repetition was applied when transmitting the random access message.
 16. The method of claim 1, wherein transmitting the random access message comprises transmitting with a format of a preamble that indicates a modulation and coding scheme for a physical uplink shared channel included in the random access message.
 17. The method of claim 1, further comprising determining whether the signal strength satisfies the second signal strength threshold, wherein a resource allocation of a physical uplink shared channel (PUSCH) occasion and a selection of a PUSCH resource unit, relative to a RACH occasion, is based at least in part on the determination of whether the signal strength satisfies the second signal strength threshold.
 18. The method of claim 17, further comprising receiving system information that identifies information associated with the resource allocation of the PUSCH occasion and the selection of the PUSCH resource unit relative to the RACH occasion.
 19. The method of claim 1, further comprising: receiving a synchronization signal block (SSB); and determining the signal strength based at least in part on a reference signal received power associated with the SSB.
 20. The method of claim 1, further comprising: receiving configuration information associated with the second message type, the configuration information including information associated with at least one of: a physical random access channel (PRACH) format; application of physical uplink shared channel (PUSCH) repetition; a modulation and coding scheme; a payload size; a resource allocation for PUSCH; application of preamble repetition; or a preamble length.
 21. The method of claim 20, further comprising receiving the configuration information in at least one of: a synchronization signal block; system information; a physical downlink control channel; or remaining minimum system information.
 22. A method of wireless communication performed by a network entity, comprising: transmitting information that identifies a first signal strength threshold associated with determining to use a message type, wherein the first signal strength threshold is greater than a second signal strength threshold associated with determining to use a two-step random access channel (RACH) procedure; receiving, from a user equipment (UE), a random access message associated with the two-step RACH procedure; determining, based at least in part on the random access message, the message type of the random access message, wherein the message type is either a first message type or a second message type, the first message type being different from the second message type; and processing the random access message based at least in part on determining the message type of the random access message.
 23. The method of claim 22, wherein the first message type includes a message type of a first message in the two-step RACH procedure and the second message type includes a coverage enhanced message type of the first message in the two-step RACH procedure.
 24. The method of claim 22, wherein the information is system information.
 25. The method of claim 22, wherein processing the random access message comprises at least one of: processing based on a physical random access channel (PRACH) format, wherein the PRACH format when the first message type is determined is different from the PRACH format when the second message type is determined; processing based on a determination of whether physical uplink shared channel (PUSCH) repetition is applied, wherein PUSCH repetition is determined not to be applied if the first message type is determined and PUSCH repetition is determined to be applied if the second message type is determined; processing based on a modulation and coding scheme (MCS), wherein the MCS when the first message type is determined is different from the MCS when the second message type is determined; processing based on a payload size, wherein the payload size when the first message type is determined is different from the payload size when the second message type is determined; processing based on a PUSCH resource allocation, wherein the PUSCH resource allocation when the first message type is determined is different from the PUSCH resource allocation when the second message type is determined; processing based on a determination of whether preamble repetition is applied, wherein preamble repetition is determined not to be applied if the first message type is determined and preamble repetition is determined to be applied if the second message type is determined; or processing based on a preamble length, wherein the preamble length when the first message type is determined is different from the preamble length when the second message type is determined.
 26. The method of claim 22, wherein receiving the random access message comprises receiving an indication of whether physical uplink shared channel (PUSCH) repetition was applied when transmitting the random access message, and wherein the indication is at least one of a preamble sequence included in the random access message or a format of a preamble of the random access message, the preamble sequence being one of a set of preamble sequences associated with indicating application of PUSCH repetition.
 27. The method of claim 22, wherein receiving the random access message comprises receiving an indication of a modulation and coding scheme (MCS) for a physical uplink shard channel included in the random access message, and wherein the indication is a format of a preamble of the random access message.
 28. A user equipment (UE) for wireless communication, comprising: a memory; and one or more processors configured to: determine that the UE is to use a two-step random access channel (RACH) procedure based at least in part on a first signal strength threshold; determine a message type for a random access message associated with the two-step RACH procedure, wherein the message type is either a first message type or a second message type, the first message type being different from the second message type, wherein the message type is determined based at least in part on whether a signal strength satisfies a second signal strength threshold, and wherein the second signal threshold is greater than the first signal strength threshold; and transmit the random access message based at least in part on the determined message type.
 29. The UE of claim 28, wherein the message type is determined to be the first message type when the signal strength satisfies the second signal strength threshold, and is determined to be the second message type when the signal strength does not satisfy the second signal strength threshold.
 30. A base station for wireless communication, comprising: a memory; and one or more processors configured to: transmit information that identifies a first signal strength threshold associated with determining to use a message type, wherein the first signal strength threshold is greater than a second signal strength threshold associated with determining to use a two-step random access channel (RACH) procedure; receive, from a user equipment (UE), a random access message associated with the two-step RACH procedure; determine, based at least in part on the random access message, the message type of the random access message, wherein the message type is either a first message type or a second message type, the first message type being different from the second message type; and process the random access message based at least in part on determining the message type of the random access message. 